|
A design rationale is an explicit documentation of the reasons behind decisions made when designing a system or artifact. As initially developed by W.R. Kunz and Horst Rittel, design rationale seeks to provide argumentation-based structure to the political, collaborative process of addressing wicked problems.〔 == Overview == A design rationale is the explicit listing of decisions made during a design process, and the reasons why those decisions were made.〔Jarczyk, Alex P.; Löffler, Peter; Shipman III, Frank M. (1992), "Design Rationale for Software Engineering: A Survey", ''25th Hawaii International Conference on System Sciences'', 2, pp. 577-586〕 Its primary goal is to support designers by providing a means to record and communicate the argumentation and reasoning behind the design process.〔Horner, J.; Atwood, M.E. (2006), "Effective Design Rationale: Understanding the Barriers", in Dutoit, A.H.; McCall, R.; Mistrík, I. et al., Rationale Management in Software Engineering, Springer Berlin Heidelberg, pp. 73-90〕 It should therefore include:〔Lee, J. (1997). "Design Rationale Systems: Understanding the Issues". ''IEEE Expert'' 12 (3): 78–85〕 * the reasons behind a design decision, * the justification for it, * the other alternatives considered, * the trade offs evaluated, and * the argumentation that led to the decision. Several science areas are involved in the study of design rationales, such as Computer Science〔 Cognitive Science,〔 Artificial Intelligence,〔Burge, J.E.; Brown, D.C. (2000), "Reasoning with Design Rationale", in Gero, J., ''Artificial Intelligence in Design '00'', Netherlands: Kluwer Academic Publ., pp. 611–629〕 and Knowledge Management〔Xin, W.; Guangleng, X. (2001), "Design Rationale as Part of Corporate Technical Memory", ''Systems, Man and Cybernetics'', pp. 1904 - 1908.〕 For supporting design rationale, various frameworks have been proposed, such as QOC, DRCS, IBIS, and DRL. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Design rationale」の詳細全文を読む スポンサード リンク
|